System and method of binding a client to a server

ABSTRACT

Systems and methods to bind a client with a server are provided. A particular method includes establishing a connection between a server and a client. A list of best-fit server IP addresses is received at the client via the connection. A determination is made whether the server is identified in the list of best-fit server IP addresses. When the server is not identified in the list of best-fit server IP addresses, the connection to the server is terminated.

CLAIM OF PRIORITY

The present application claims priority from and is a continuation of patent application Ser. No. 11/043,680 filed on Jan. 26, 2005 and entitled “SYSTEM AND METHOD OF BINDING A CLIENT TO A SERVER,” which claims priority under 35 U.S.C. §119(e) to provisional patent application 60/539,768 filed on Jan. 28, 2004, the contents of both of which are expressly incorporated herein by reference in their entirety.

FIELD OF THE DISCLOSURE

The present disclosure relates generally to implementation of client-server networks. More particularly, the disclosure provides systems and methods for maintaining the binding of a client, particularly a client with limited computational and storage resources, with at least one server.

BACKGROUND

The Internet has had a profound impact on the way society communicates. Today, the Internet is used for personal communications, for business communications, for shopping, for entertainment, for news, and more.

There are many applications that rely on a client being in constant contact with a server in order to perform a task. The client to server connection (binding) may be mission critical and may be maintained constantly. For example, an interruption in communications of approximately thirty seconds within a one-hour interval may be intolerable. Factors that may influence the client being in constant contact with the server include:

-   -   The client may reside on a small, specialized computer, with         limited computational and storage resources (herein, an         “Internet Appliance”).     -   To remove the potential for a “single point of failure” multiple         servers may be deployed, geographically separated and         independently addressable on the Internet. The number of servers         may range into the hundreds.     -   When many clients (e.g., millions of clients) are expected,         clients may be distributed across available servers to reduce         the impact of a server failing and to maintain responsiveness of         client/server bindings.     -   The binding between client and server may be dynamic. There are         many potential causes for a client to need to change the server         to which it is bound.

The desire for dynamic binding between a client and server may be related to a number of factors. To ensure that combined server resources are being allocated to provide optimal service to all clients, clients are distributed among servers. The distribution takes into account the “routing distance” between a client and the server (the number of Internet hops as well as message delivery latency). As more clients are added, the distribution may become sub-optimum and adjustment may be appropriate. In turn, some clients may be redirected to different servers. Another benefit of dynamic binding between client and server may be to provide for continuity of client services in the event a server fails or is pulled off-line for maintenance.

One approach for a client to identify and then bind with a server relies on the Internet Distributed Name Service (DNS), which can associate a static list of Internet IP addresses with a name. While machines respond to IP addresses in the form of number strings, humans are not as adept at remembering number strings. A name server (or DNS server) receives a name from a client, associates the name with an IP address, and sends the IP address to a client. The client then communicates with a server via the server's IP address.

The DNS is, however, far from simple. Name servers may receive millions of requests each day. Because a single name server may not know the address associated with a particular name, name servers may also be able to contact other name servers. A name server may start its search for an IP address by contacting one of the root name servers. The root name servers may know the IP address for all of the name servers that handle the top-level domains. For example, a name server might “ask” a root name server for the IP address associated with www.yahoo.com, and the root name server might “respond” (assuming no caching), that it does not know the IP address for www.yahoo.com, and instead provide the IP address for the COM name server. One of the keys to making this work is redundancy. There may be multiple name servers at every level, so if one fails, there are others to handle the requests.

To speed up the process, name servers may cache the IP addresses returned in response to requests. Name servers may not cache forever, though. The caching may use a component, called the Time To Live (TTL) that controls how long a name server will cache a piece of information. When a name server receives an IP address, it may receive the TTL with it. The name server may cache the IP address for that period of time (ranging from minutes to days) and then discard it. Using TTL enables changes to propagate to the name servers.

Not all name servers respect the TTL they receive, however. This means that new information and old information may reside in the DNS at the same time. Sometimes, it may take weeks for a change in an IP address to propagate throughout the Web. Additionally, implementing a DNS protocol on an Internet Appliance may require additional computational, program storage and data storage resources that may not be available or desirable to add.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates the interaction of an Internet Appliance with a server according to particular embodiments.

FIG. 2 illustrates a process according to particular embodiments in which an Internet Appliance (client) uses best-fit IP address to create a binding with a server.

FIG. 3 illustrates a process of receiving and verifying a best-fit list by a client according to particular embodiments.

DETAILED DESCRIPTION

Embodiments disclosed herein enable a client to receive and maintain a set of “best-fit” server IP addresses. The best fit server IP addresses establish a hierarchy of server addresses that are used by a client to maintain a binding with a server without using the DNS. In the case of an Internet Appliance, the set of best-fit server IP addresses may be relatively small. In one embodiment, an Internet Appliance maintains a set of three best-fit server IP addresses. However, this is not meant as a limitation. As will be apparent to those skilled in the art, any number of best-fit server IP addresses may be maintained by a client/Internet Appliance without departing from the scope of the present disclosure. Communicating the set of best-fit server IP addresses to a specific client may be accomplished using extensions of a network protocol already used to support client/server communications, thus minimizing the amount of code needed to support the additional information transfer.

It is therefore an aspect of particular embodiments to provide and maintain a set of best-fit server IP addresses with a client.

It is an aspect of particular embodiments to provide a set of best-fit server IP addresses to a client via a protocol used by the client and server to establish and/or conduct communications.

It is an aspect of particular embodiments to use a set of best-fit server IP addresses to dynamically bind a client with a server, either at the initialization of a session between the client and server or as a result of a loss of connectivity between the client and server, without using DNS.

Another aspect of particular embodiments is to minimize overhead required to dynamically bind a client with a server without using DNS.

These and other aspects of particular embodiments will become apparent from a review of the general and detailed descriptions that follow.

A particular embodiment provides a method for maintaining the binding of a client with a server. A server creates a list including of a list of best-fit server IP addresses for a client. Optionally, the list of best-fit server IP addresses are ordered according to network distribution criteria, such as a routing distance between the client and each server associated with each of the list of best-fit server IP addresses, a message delivery latency, and server loading. A transmission protocol used by the client and the server is extended for communications to transport the best-fit server IP list. The best-fit server IP list is sent to the client. In another embodiment, a Session Initiation Protocol (SIP) protocol message is extended and the best-fit server IP list is sent to the client using the extended SIP protocol message including the best-fit server IP list.

Another particular embodiment provides a method for initiating the binding of a client with a server. A best-fit server IP address is selected by a client from a list of best-fit server IP addresses. An attempt is made by the client to initiate a session with a server using the selected best-fit server IP address. In the event the first attempt to initiate a session fails, a next best-fit server IP address is selected from a best-fit server IP address list. The client makes a next attempt to initiate a session with a server using the next selected best-fit server IP address. In another embodiment, the best-fit server IP address list is ordered according to network distribution criteria. Optionally, the distribution criteria may include a routing distance between the client and each server associated with each of the list of best-fit server IP addresses, message delivery latency, and server loading. Selecting the first and next best-fit server IP addresses from a best-fit server IP address list includes selecting the best-fit server IP addresses according to the order in which the best-fit server IP addresses appear on the best-fit server IP address list.

Another particular embodiment provides a method for maintaining the binding of a client with a server. A transmission protocol used by the client and the server is extended for communications. The extended transmission protocol is used by the client to request a best-fit server IP list from the server, wherein the best-fit server IP list includes a list of best-fit server IP addresses. The best-fit server IP list is received and stored by the client. In an embodiment, a Simple Traversal of User Datagram Protocol through Network Address Translators (NATs) (STUN) protocol message is extended and used to request the best-fit server IP list.

In yet another embodiment, the client determines whether the IP address of a server is on the best-fit IP address list. In the event that the server is not on the best-fit IP address list, the client terminates its association with the server and selects a best-fit server IP address from a best-fit server IP address list. An attempt may be made by the client to initiate a session using the selected best-fit server IP address. In the event the first attempt to initiate a session fails, a next best-fit server IP address may be selected from the best-fit server IP address list. A next attempt may be made by the client to initiate a session using the next selected best-fit server IP address. Optionally, the best-fit server IP addresses may be ordered according to network distribution criteria. The network distribution criteria may include a routing distance between the client and each server associated with each of the list of best-fit server IP addresses, message delivery latency, and server loading.

In another embodiment, the client determines whether a connection between the client and a server has been lost. In the event that the connection has been lost, a best-fit server IP address is selected from the best-fit server IP address list. An attempt is made by the client to initiate a session using the selected best-fit server IP address. In the event the first attempt to initiate a session fails, a next best-fit server IP address is selected from a best-fit server IP address list. The client makes a next attempt to initiate a session using the next selected best-fit server IP address.

Optionally, the best-fit server IP addresses may be ordered according to network distribution criteria. The network distribution criteria may include a routing distance between the client and each server associated with each of the list of best-fit server IP addresses, message delivery latency, and server loading.

Embodiments enable a client to receive and maintain a set of “best-fit” server IP addresses. The best fit server IP addresses may establish a hierarchy of server addresses that may be used by a client to maintain a binding with a server without using the DNS. In the case of an Internet Appliance, the set of best-fit server IP addresses may be relatively small. In one embodiment, an Internet Appliance maintains a set of three best-fit server IP addresses. Communicating the set of best-fit server IP addresses to a specific client may be accomplished using extensions of network protocols already used to support client/server communications, thus minimizing the amount of code needed to support the additional information transfer.

FIG. 1 illustrates the interaction of an Internet Appliance with a server according to particular embodiments. Referring to FIG. 1, an Internet Appliance (client) 100 includes a protocol engine 110 connected to the Internet 115. The protocol engine 110 communicates via the Internet 115 with a corresponding protocol engine 145 in a server 140. As part of this communication, a protocol message 160 listing best-fit server IP addresses is passed from the server 140 to the Internet Appliance (client) 100. The Internet Appliance (client) 100 extracts this information from the protocol message 160 and saves this information in persistent memory (not illustrated) as a best-fit server IP list 105.

In order to construct the protocol message 160 including the best-fit IP addresses, the protocol engine 145 on the server 140 is integrated with a best-fit solutions database 155. In this embodiment, the best-fit solutions database 155 is updated by an optimizer program 150 that runs as a background application on the server 140. However, this is not meant as a limitation. As would be apparent to those skilled in the art, other means may be used to create the best-fit IP addresses. By way of illustration and not as a limitation, in an embodiment, the best-fit IP addresses are computed on-the-fly (by the protocol engine 145 or a linked device) based on the latest routing and server availability information.

FIG. 2 illustrates a process according to embodiments in which an Internet Appliance (client) uses best-fit IP address to create a binding with a server. Referring to FIG. 2, a client initiates contact with a server using a first best-fit IP address in a list at 200. If the connection is bound at 210, the binding process ends at 230. If the client is not bound to a server at 210, a check is made at 215 to determine if the last-tried best-fit address was the last address. If the last-tried best-fit address was the last address, the binding process is restarted at 225. If the last-tried best-fit address is not the last address, contact is initiated using the next best-fit address at 220.

When a binding is successful (at 230), the connection may be checked at 235 to determine if the connection has been lost at 240. If the connection has not been lost at 240, the checking process is repeated at 235. If the connection has been lost, the binding process is restarted at 225. If none of the servers in the best-fit server IP address list (shown in FIG. 1 at 105) responds then, a “catastrophic” failure has occurred. This could be because the user's Internet access has been impaired, because a sufficiently large part of the Internet is disabled preventing access to any of the servers in the best-fit list, or because a sufficiently large physical event has caused all the servers in the best-fit list to become inoperable. When a “catastrophic” failure occurs, the client continues to contact the servers on its best-fit server IP list until the network problem is corrected. This re-use of the initialization procedure helps address the constraint of scarce storage resources on the Internet Appliance.

In an embodiment, the list of best-fit server IP addresses (shown in FIG. 1 at 105) is ordered such that elements closer to the top of the list are “more optimal” than lower items on the list. Thus, the binding process illustrated in FIG. 2 attempts to bind with the more optimal server first. In this context, “more optimal” reflects the result of analysis done prior to the last download of the best-fit list from the server to the client. Note subsequent to the last sending of the best-fit list and the time when the client is bound to a server, the physical location or Internet “routing distance” may have changed thereby changing the optimization of the best-fit list.

FIG. 3 illustrates a process of receiving and verifying a best-fit server IP address list by a client according to particular embodiments. Referring to FIG. 3, a client binds with a server at 300. A new best-fit server IP address list is received and stored by the client 305 for access during power up initialization. Once stored, the client determines whether it is currently bound to a server having the first best-fit address in the new list at 310. If it is not, then the client initiates a binding process as illustrated in FIG. 2. If the client is currently bound to the server having the first best-fit server IP address in the new best-fit server IP address list, the validation process ends at 315.

As previously noted, the server may determine the best-fit list of server IP addresses and may communicate this information to the client via a extension of a network protocol currently used by the client and server to establish or maintain existing communications. In an embodiment, a protocol engine at the server is extended to accept a best-fit server IP address list and communicate it to each client associated with that server. In the event the server associated with a client is no longer on the list of best-fit server IP addresses, the client will terminate the association and attempt to connect with a server on the last-received list. The server represented by the first server IP address on the new best-fit server IP address list is then associated with the client.

In a particular embodiment, a network protocol used by a client and server to convey information relating to the best-fit server IP address list is extended. In order to avoid issues with firewalls and network address translation systems, a preferred protocol may support sessions initiated by the client that allow subsequent responses by the server. Additionally, the preferred protocol may support communication at a frequency that facilitates timely communication of new best-fit server IP address lists and may be adaptable to accept the simple payload data used for the best-fit server IP address list.

In an exemplary embodiment, a client and server use multiple protocols to send and update best-fit server IP address information. By way of illustration and not as a limitation, a server may communicate with a client via Session Initiation Protocol (SIP). This protocol meets the preferred criteria that a session is initiated by the client while allowing the server to send the client a message at any time. However, processing of the SIP protocol for both the client and the server requires considerable work. This is of particular concern where the client resides on an Internet Appliance with very little computation resources. In addition to SIP, the client in this exemplary embodiment may also use the Simple Traversal of User Datagram Protocol through Network Address Translators (NATs) (STUN) protocol. STUN lacks that quality of being able to respond to a server-generated message at any time, but has the advantage that it is very simple to process and extend. These two protocols, however, may be used in combination to perform the tasks of sending a list of best-fit server IP addresses to the client and sending the client notice that the list has been updated. The server may use a SIP protocol extension to notify the client. The client may use the STUN protocol to request and receive the new list.

A system and method for permitting a client running on an Internet Appliance to dynamically bind with at least one server without using DNS has been illustrated. It will be understood by those skilled in the art that the present disclosure may be embodied in other specific forms without departing from the scope of the disclosure and that the examples and embodiments described herein are in all respects illustrative and not restrictive. Those skilled in the art will recognize that other embodiments using the concepts described herein are also possible. 

1. A method of binding a client to a server, the method comprising: establishing a connection between a server and a client; receiving, at the client via the connection, a list of best-fit server Internet Protocol (IP) addresses; determining whether the server is identified in the list of best-fit server IP addresses; and terminating the connection to the server when the server is not identified in the list of best-fit server IP addresses.
 2. A server device, comprising: a processor; a memory accessible to the processor; and a protocol engine executable by the processor to: establish a connection to a client device; and send a list of best-fit server Internet Protocol (IP)addresses to the client device via the connection, wherein the list of best-fit server IP addresses is determined based on network distribution criteria; wherein the client device terminates the connection to the server device when the server device is not on the list of best-fit server IP addresses.
 3. A client device, comprising: a processor; a memory accessible to the processor; a protocol engine executable by the processor to: establish a connection between a server and the client device; receive, at the client device via the connection, a list of best-fit server Internet Protocol (IP) addresses; and determine whether the server is identified in the list of best-fit server IP addresses; and terminate the connection to the server when the server is not identified in the list of best-fit server IP addresses. 